1 Overview

In this course:

• The calculation of your final letter grade will be based, in part, on your completion of a team-oriented software engineering project.
• Participation in and completion of the software design and development project is strictly required. If you do not actively participate in the project you will receive a grade of "F" for the course.

2 Collaboration

You will be assigned to a team for the project. Without exception, each team must work on each part of the project independently. That is, while working on a particular part of the project, members of one team must not discuss the assignment with members of another team.

3 Third-Party Libraries/Code

You must design and implement all of the code used in the product. In other words, you may not use any third-party libraries. You may use third-party data and/or icons, provided that you do not infringe on any copyrights (or copylefts).

4 Intra-Team Communications

For the most part, you may communicate with other members of your team in any way you like. However, whenever possible, you should keep a written record of the communications since you may be asked to justify both your decisions and your assessments of team members.

For some parts of the project, you may be required to communicate in particular ways (e.g., using email, an issue tracking tool, etc...).

5 Time Allocation

A full-time student is expected to work 40-45 hours per week in total (comparable to a full-time employee). Since a full-time student typically takes 5 courses, a student is expected to work (on average) 8-9 hours per week.

Assuming 6 weeks of the semester is devoted to the project, the typical student is expected to work 48-54 hours on the project. Assuming that the project is divided into 3 sprints, the typical student is expected to work 16-18 hours on each sprint. (So, if 4 hours is devoted to planning, the typical students is expected to devote 12-16 hours to other aspects of the sprint.)

6 Due Dates

Deliverables may not be submitted for a grade after the due date. You may submit them for feedback but, deliverables submitted after the due date will receive a grade of 0.

7 Submission

If things work as planned, all of your code and planning documents will be managed with the course-approved tools and will be available to the Professor continuously. Nonetheless, at the completion of the project you will need to submit a variety of things. Details will be provided to you.

8 Team Evaluation

At the end of the project you must complete the Team Evaluation Form.

9 Presentations

Teams may be required to present their progress in class. Teams must be prepared to present the final product on the "due date".

10 Attendance

Attendance is mandatory on days when group/team activities and meetings are scheduled.

11 Grading

The project will be completed in a series of sprints, each of which will consist of a planning phase and an execution phase. Typically, all members of the team will receive the same grade for the planning phases (though there may be exceptions) and each member of the team will be graded individually for the execution. At the end of the last sprint, each member of the team will receive a grade for the project that will be based on the team planning grades, the individual execution grade, the final presentation, and the team evaluations (see above).